Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1017

reference
444-tree-1
name
1017
tree-preservation-order

undefined

444-tpo-1
uprn
address-text
point
POINT (-1.023857 50.897604)
geometry
MULTIPOLYGON (((-1.023757 50.897594,-1.023762 50.897613,-1.023776 50.897631,-1.023797 50.897645,-1.023825 50.897654,-1.023856 50.897658,-1.023886 50.897655,-1.023914 50.897646,-1.023937 50.897632,-1.023951 50.897615,-1.023956 50.897595,-1.023952 50.897576,-1.023938 50.897558,-1.023917 50.897544,-1.023889 50.897535,-1.023858 50.897532,-1.023827 50.897535,-1.023800 50.897543,-1.023777 50.897557,-1.023763 50.897574,-1.023757 50.897594)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL